managing requirement variants

hi

we have a product with differing reqts for differing releases/variants and i was just wondering if anyone had found a way to successfuly manage this in doors modules?

we want to keep all reqts for variants in one reqts spec - was thinking of tagging reqts for variant 1 variant 2 etc - the only thing is when i baseline the yellow status bar will change and you wont easily know whats changed / new?

any suggestions or experience - i would greatly appreciate

thanks


doorsuser77 - Wed Dec 18 11:53:22 EST 2013

Re: managing requirement variants
mhersey - Wed Dec 18 16:39:58 EST 2013

I'm not a top flight DOORs expert but from a process perspective the Tagging idea only really works if you can be sure of a small and limited number of variations.  The problem is that a variation in a requirement is often seen as just a different requirement.

One place where this idea comes to the front is when you have a formal product line platform.  Here what you have is not so much a different requirement but a selected variation within a specified range. i.e. the platform specifies the exact limits on the variation allowed and takes the responsibility for verifying all that range.  Variation can be accomplished by specifying the range e.g. "...from 4 to 7.5 mm" in which case "6" is fine. Or by specifying allowed options i.e. the attribute can be any one of {4mm; 5mm; or 7.5mm} in which case "6" is not fine.

Either way the rule usually comes to the following: Specify the generally true part within the platform (sometimes called the domain).  Specify the actual value within the specific project or application.

This way you try to get the best of both worlds: you can link the platform requirement acting as a constraint and so provide the coupling between the specific variation needed.  In this case you only baseline the actual product requirements which stand by themselves but the baseline does not lose the connection to the underlying constraint captured in the domain engineering portion.

When the scale of this problem becomes large there are products out there that help you keep track of this.  e.g. http://www.biglever.com/solution/product.html with bridges to DOORS

Re: managing requirement variants
llandale - Wed Dec 18 17:00:40 EST 2013

mhersey - Wed Dec 18 16:39:58 EST 2013

I'm not a top flight DOORs expert but from a process perspective the Tagging idea only really works if you can be sure of a small and limited number of variations.  The problem is that a variation in a requirement is often seen as just a different requirement.

One place where this idea comes to the front is when you have a formal product line platform.  Here what you have is not so much a different requirement but a selected variation within a specified range. i.e. the platform specifies the exact limits on the variation allowed and takes the responsibility for verifying all that range.  Variation can be accomplished by specifying the range e.g. "...from 4 to 7.5 mm" in which case "6" is fine. Or by specifying allowed options i.e. the attribute can be any one of {4mm; 5mm; or 7.5mm} in which case "6" is not fine.

Either way the rule usually comes to the following: Specify the generally true part within the platform (sometimes called the domain).  Specify the actual value within the specific project or application.

This way you try to get the best of both worlds: you can link the platform requirement acting as a constraint and so provide the coupling between the specific variation needed.  In this case you only baseline the actual product requirements which stand by themselves but the baseline does not lose the connection to the underlying constraint captured in the domain engineering portion.

When the scale of this problem becomes large there are products out there that help you keep track of this.  e.g. http://www.biglever.com/solution/product.html with bridges to DOORS

Is the following a reasonable application for what you said?

  • The Standard Product Satelite can have a service life of 5-15 years and can handle 500-3000 transactions per second.
  • Customer ABC wants a Satelite with 8 year lifespan and 1000 transactions per minute.
  • The Standard Product Satelite can withstand an impact in the range G-H.
  • Customer ABC needs it to withstand an impact of G.

The Satelite requirements at my former company, I must say, did not have a range.  They had a standard Statelite, and Customers can request variations of it. So if it's lifespan is 10 years, they did not do reasonable studies to determine that they could reasonably adjust that for 5-15 years; until some customer desires something non-standard.  Then they do trade studies seeing how much money they could save by reducing the life span.

-Louie

Re: managing requirement variants
mhersey - Wed Dec 18 17:18:24 EST 2013

llandale - Wed Dec 18 17:00:40 EST 2013

Is the following a reasonable application for what you said?

  • The Standard Product Satelite can have a service life of 5-15 years and can handle 500-3000 transactions per second.
  • Customer ABC wants a Satelite with 8 year lifespan and 1000 transactions per minute.
  • The Standard Product Satelite can withstand an impact in the range G-H.
  • Customer ABC needs it to withstand an impact of G.

The Satelite requirements at my former company, I must say, did not have a range.  They had a standard Statelite, and Customers can request variations of it. So if it's lifespan is 10 years, they did not do reasonable studies to determine that they could reasonably adjust that for 5-15 years; until some customer desires something non-standard.  Then they do trade studies seeing how much money they could save by reducing the life span.

-Louie

Mixed:

  • Service life 5-15 years is not so much a requirement more a wish; even if recast to service life shall be more than 5 years it is not really a requirement with variation.  So a need for 8 years will involve fresh engineering and not "reuse"
  • Can handle 500-3000 transactions per second: Yes that's more like it as long as the performance of the whole range has been verified
  • Can withstand impacts of G to H: yes if these are tightly defined enough to be verifiable options.